fix(reviewer-bot): clarify /release command behavior and guidance#410
fix(reviewer-bot): clarify /release command behavior and guidance#410PLeVasseur wants to merge 1 commit into
Conversation
✅ Deploy Preview for scrc-coding-guidelines ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@PLeVasseur should it be From the context of where the command is invoked, it would always know who the current reviewer is, right? |
|
@guidelines-bot /r? producers |
|
@cpetig is designated as reviewer by queue rotation, but GitHub could not add them to PR Reviewers automatically (API 422). A triage+ approver may still be required before merge queue. |
|
✅ @cpetig remains designated as reviewer in bot state. GitHub reviewer assignment could not be completed. |
github-actions
Bot
added
the
status: awaiting reviewer response
|
@PLeVasseur do we need to get this merged in? |
Yeah, that'd probably be wise. I need to reorient myself. Next week looks more open for me to do that. |
4 participants
Summary
/releaseusage explicit everywhere the bot documents commands by splitting self release and triage release forms/releasefailure messaging for non current reviewers with actionable guidance that points to/release @current-reviewer/commandsoutput, and the confusing non current reviewer release pathsTesting
uv run ruff check --fix scripts/reviewer_bot.py .github/reviewer-bot-tests/test_reviewer_bot.pyuv run python -m pytest .github/reviewer-bot-tests/test_reviewer_bot.py -k releaseuv run python -m pytest .github/reviewer-bot-tests/test_reviewer_bot.pyCloses #406